Method, system and apparatus for dynamically generating map textures

ABSTRACT

Methods, systems and apparatus are described to dynamically generate map textures. A client device may obtain map data, which may include one or more shapes described by vector graphics data. Along with the one or more shapes, embodiments may include texture indicators linked to the one or more shapes. Embodiments may render the map data. For one or more shapes, a texture definition may be obtained. Based on the texture definition, a client device may dynamically generate a texture for the shape. The texture may then be applied to the shape to render a current fill portion of the shape. In some embodiments the render map view is displayed.

This application claims benefit of priority to U.S. ProvisionalApplication Ser. No. 61/698,797, entitled “Method, System And ApparatusFor Dynamically Generating Map Textures,” filed Sep. 10, 2012.

This application is a continuation-in-part of U.S. application Ser. No.13/619,472 entitled “Method, System, And Apparatus for Rendering A MapAccording To A Stylesheet” filed Sep. 14, 2012, which claims benefit ofpriority to U.S. Provisional Application Ser. No. 61/655,900, entitled“Method, System And Apparatus For Rendering A Map According To AStylesheet,” filed Jun. 5, 2012, the content of which are incorporatedby reference herein in their entirety.

This application is a continuation-in-part of U.S. application Ser. No.13/601,940 entitled “Method, System, And Apparatus for Rendering A MapAccording To Texture Masks” filed Aug. 31, 2012, which claims benefit ofpriority to U.S. Provisional Application Ser. No. 61/655,869, entitled“Method, System And Apparatus For Rendering A Map According To TextureMasks,” filed Jun. 5, 2012, the content of which are incorporated byreference herein in their entirety.

BACKGROUND Description of the Related Art

Mobile computing is an expanding field of technological development.Advances in mobile communications, mobile hardware, and mobile softwareapplications are continually developing new solutions for existinglimitations in the field and providing innovative products forconsumers. As part of the growing demand for mobile softwareapplications, map displays and navigation applications provide a userwith various forms of maps, navigation, and direction information.Often, map data is manipulated and displayed by mobile devices, such asmobile phones, personal digital assistants, tablet computers, or laptopcomputers. Interactivity with these applications increases theprocessing demand on a mobile device which, if not accounted for, maylead to bad user experiences or application failure. To account for anapplication's demand on a mobile device's resources, applicationdesigners may attempt to reduce the size or quantity of transactionsnecessary to perform mobile software applications.

SUMMARY

Various embodiments of methods, apparatus, and computer-readable storagemedia for dynamically generating map textures are described. A mapapplication implemented on a client device may obtain map data thatdescribes one or more map features. Textures may be dynamicallygenerated for map features by the map application on the client devicebased on a texture definition, removing the necessity of downloadingtextures, and thus saving data transfer bandwidth. Texture definitionsmay be obtained from a map service. Texture definitions may also specifyblending texture layers and noise texture elements or pattern textureelements to generate a texture. In some embodiments, texture definitionsmay change in response to various conditions or user selections. Textureanimations may also be defined in texture definitions. Generatedtextures may be stored locally on a client device, as can texture layersand noise texture elements or pattern texture elements used to generatetextures. Dynamically generated textures may then be applied to the mapfeatures in order to render the map features for display. A map view maybe displayed with map features filled with the generated textures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a map service operating environment,according to some embodiments.

FIG. 2 illustrates a high-level flowchart of a method of dynamicallygenerating map textures, according to some embodiments.

FIG. 3A illustrates a high-level flowchart of a method of blendingtexture layers and elements to generate a texture, according to someembodiments.

FIG. 3B illustrates the combination of texture layers and elements,according to some embodiments.

FIG. 4 illustrates a map module that implements dynamically generatingmap textures, according to some embodiments.

FIG. 5 illustrates an example electronic device, according to texturemasks according to some embodiments.

FIG. 6 illustrates an example electronic device, according to someembodiments.

FIG. 7 illustrates an example electronic device, according to someembodiments.

FIG. 8 illustrates an example electronic device, according to someembodiments.

FIG. 9 illustrates an example system, according to some embodiments.

While the invention is described herein by way of example for severalembodiments and illustrative drawings, those skilled in the art willrecognize that the invention is not limited to the embodiments ordrawings described. It should be understood, that the drawings anddetailed description thereto are not intended to limit the invention tothe particular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents and alternatives falling within thespirit and scope of the present invention. The headings used herein arefor organizational purposes only and are not meant to be used to limitthe scope of the description. As used throughout this application, theword “may” is used in a permissive sense (i.e., meaning having thepotential to), rather than the mandatory sense (i.e., meaning must).Similarly, the words “include”, “including”, and “includes” meanincluding, but not limited to.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, methods, apparatus, or systems that would be known by one ofordinary skill have not been described in detail so as not to obscureclaimed subject matter.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Some portions of the detailed description which follow are presented interms of algorithms or symbolic representation of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software andother programmable electronic devices. Algorithmic descriptions orsymbolic representations are examples of techniques used by those ofordinary skill in the signal processing or related arts to convey thesubstance of their work to others skilled in the art. An algorithm ishere, and is generally, considered to be a self-consistent sequence ofoperations or similar signal processing leading to a desired result. Inthis context, operations or processing involve physical manipulation ofphysical quantities. Typically, although not necessarily, suchquantities may take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared or otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to such signals as bits, data, values,elements, symbols, characters, terms, numbers, numerals or the like. Itshould be understood, however, that all of these or similar terms are tobe associated with appropriate physical quantities and are merelyconvenient labels.

Various embodiments of methods, apparatus, and computer-readable storagemedia for dynamically generating map textures are described. Severalembodiments of generating textures are described that may be suitablefor rendering map data, which may describe one or more shapes for a map.Map data may be obtained by a client device, such as client devices 102described in FIG. 1 below, from a server or service implemented on aserver, such as map service 130 described in FIG. 1 below. Vectorgraphics data may be included within map data to describe shapes. Alsoincluded with map data may be texture identifiers linked to thedescribed one or more shapes. Map data may also describe other areasdistinct from the shapes. These other shapes or areas may include othertypes of graphics data, such as raster graphics data, or additionalvector graphics data. Map data may be obtained in various formats, suchas one or more map tiles described below with regard to FIG. 1.

A map view may be rendered for display by a client device based upon theobtained map data, in some embodiments. For one or more describedshapes, a client device may obtain a particular texture definition forthe shape. This texture definition may be obtained based on a textureidentifier. A texture identifier may be obtained along with other mapdata from a map service. Texture identifiers may be linked to one ormore shapes described in the map data. For example, a texture identifiermay be a park texture identifier. Each shape in the map data thatrepresents a park may be linked to the park texture identifier. Ingeneral, a client device may obtain a particular texture definition froma server, such as a map server, or a resource local to the clientdevice, such as local memory or another module implemented on the clientdevice.

A client device may, in various embodiments, dynamically generatetextures for the described shapes according to the particular texturedefinitions for the shapes. A texture definition may specify a texturelayer, such as color identified by an RGB value, and one or more noisetexture elements or pattern texture elements, which may be obtained orgenerated. These specified layers and elements may be blended orcombined using many different techniques to generate textures for thedescribed map shapes. Other information may be obtained by the clientdevice that adds, subtracts, modifies, or otherwise transforms theinformation specified in the texture definitions. For instance, aparticular location of the map view being rendered may modify thetexture definition for shapes drawing open land (e.g., if the map viewis rendering Antarctica, open land's texture layer color may be changedfrom green to white). Generated textures, texture layers, or noisetexture elements, may be stored locally on the client device for laterreuse.

More generally, map textures, may be, but are not limited to, imageswhich display common or repeating elements of a map view. For example, atexture may be the grass background of a larger park map view. However,they may also be larger images with varied elements. Textures may beapplied in two-dimensional and three-dimensional shapes. Some texturesmay be a texture animation, which includes a series of textures to bedisplayed in sequence. Textures may also correspond to different mapview modes, such as day or night, pedestrian or motorized vehicle, etc.

Once generated, a client device may, in some embodiments, apply thegenerated textures to render current fill portions of the shapesdescribed by the map data. Some embodiments may then display therendered map view on a display device including the shapes and theirgenerated texture current fill portions.

In at least some embodiments, a client device may obtain anotherparticular texture definition for shapes described in the map data inresponse to one or more indications of an event received at the clientdevice. Such indications may indicate a map view zoom level, map viewmode, current time, location, or ambient light of the client device,input received by the client device from one or more other modulesimplemented on the client device, indications received from a server,such as a map service, or any other form of notification of addition,subtraction, modification, or transformation of the informationspecified in one or more the texture definitions for shapes described bythe map data. In response to one of these indications, some embodimentsmay vary the current fill portion of one or more of the describedshapes, such as by obtaining another particular texture definition,dynamically generating another texture, and/or applying the othertexture to render the current fill portion of the varied shapes. In atleast some embodiments, whether the other texture is applied to vary thecurrent fill portion of a shape may be determined by whether the shapewas previously filled by a texture generated by a particular texturedefinition that has been changed.

Embodiments of dynamically generating map textures may be implemented inany application that supports map data rendering. Example categories ofapplications in which embodiments may be implemented in are maprendering, such as navigation devices, image processing applications,electronic games, and graphical design. More generally, embodiments maybe implemented in applications that allow devices to obtain map shapesand separately obtain textures to fill the map shapes in order to berendered. Some embodiments may be implemented in a map service operatingenvironment, such as map service operating environment 100 describedwith regard to FIG. 1 below. Specific examples of applications ortechnologies in which embodiments may be implemented include, but arenot limited to, map or navigation software applications on an IPODTOUCH®, IPHONE®, or IPAD® devices from Apple Inc. of Cupertino, Calif.

Embodiments of dynamically generating map textures may be implementedand performed by a module or modules implemented by program instructionsstored in a non-transitory computer-readable storage medium andexecutable by one or more processors, such as one or more CPUs or GPUs.An example module that may implement some embodiments, and an exampleapplication that may implement the module, as described herein, isillustrated in FIG. 4. An example electronic device on which embodimentsmay be implemented is illustrated in FIGS. 5 through 8. An examplesystem on which embodiments may be implemented is illustrated in FIG. 9.

Map Service Operating Environment

Various embodiments may operate within a map service operatingenvironment. FIG. 1 illustrates a map service operating environment,according to some embodiments. A map service 130 may provide mapservices for one or more client devices 102 a-102 c in communicationwith the map service 130 through various communication methods andprotocols. A map service 130 generally may provide map information andother map-related data, such as two-dimensional map image data (e.g.,aerial view of roads utilizing satellite imagery), three-dimensional mapimage data (e.g., traversable map with three-dimensional features, suchas buildings), route and direction calculation (e.g., ferry routecalculations or directions between two points for a pedestrian),real-time navigation data (e.g., turn-by-turn visual navigation data intwo or three dimensions), location data (e.g., where is the clientdevice currently located), and other geographic data (e.g., wirelessnetwork coverage, weather, traffic information, or nearbypoints-of-interest). In various embodiments, the map service data mayinclude localized labels for different countries or regions; localizedlabels may be utilized to present map labels (e.g., street names, citynames, points of interest) in different languages on client devices.Client devices 102 a-102 c may utilize these map services by obtainingmap service data. Client devices 102 a-102 c may implement varioustechniques to process map service data. Client devices 102 a-102 c maythen provide map services to various entities, including, but notlimited to, users, internal software or hardware modules, and/or othersystems or devices external to the client devices 102 a-102 c.

In some embodiments, a map service may be implemented by one or morenodes in a distributed computing system. Each node may be assigned oneor more services or components of a map service. Some nodes may beassigned the same map service or component of a map service. A loadbalancing node may distribute access or requests to other nodes within amap service. In some embodiments a map service may be implemented as asingle system, such as a single server. Different modules or hardwaredevices within a server may implement one or more of the variousservices provided by a map service.

A map service may provide map services by generating map service data invarious formats. In some embodiments, one format of map service data maybe map image data. Map image data may provide image data to a clientdevice so that the client device may process the image data (e.g.,rendering and/or displaying the image data as a two-dimensional orthree-dimensional map). Map image data, whether in two or threedimensions, may specify one or more map tiles. A map tile may be aportion of a larger map image. Assembling together the map tiles of amap may produce the original map. Tiles may be generated from map imagedata, routing or navigation data, or any other map service data. In someembodiments map tiles may be raster-based map tiles, with tile sizesranging from any size both larger and smaller than a commonly-used 256pixel by 256 pixel tile. Raster-based map tiles may be encoded in anynumber of standard digital image representations including, but notlimited to, Bitmap (.bmp), Graphics Interchange Format (.gif), JointPhotographic Experts Group (.jpg, .jpeg, etc.), Portable NetworksGraphic (.png), or Tagged Image File Format (.tiff). In someembodiments, map tiles may be vector-based map tiles, encoded usingvector graphics, including, but not limited to, Scalable Vector Graphics(.svg) or a Drawing File (.drw). Embodiments may also include tiles witha combination of vector and raster data. Metadata or other informationpertaining to the map tile may also be included within or along with amap tile, providing further map service data to a client device. Invarious embodiments, a map tile may be encoded for transport utilizingvarious standards and/or protocols, some of which are described inexamples below.

In various embodiments, map tiles may be constructed from image data ofdifferent resolutions depending on zoom level. For instance, for lowzoom level (e.g., world or globe view), the resolution of map or imagedata need not be as high relative to the resolution at a high zoom level(e.g., city or street level). For example, when in a globe view, theremay be no need to render street level artifacts as such objects would beso small as to be negligible in many cases.

A map service may perform various techniques to analyze a map tilebefore encoding the tile for transport. This analysis may optimize mapservice performance for both client devices and a map service. In someembodiments map tiles may be analyzed for complexity, according tovector-based graphic techniques, and constructed utilizing complex andnon-complex layers. Map tiles may also be analyzed for common image dataor patterns that may be rendered as image textures and constructed byrelying on image masks. In some embodiments, raster-based image data ina map tile may contain certain mask values, which are associated withone or more textures. Embodiments may also analyze map tiles forspecified features that may be associated with certain map styles thatcontain style identifiers.

Other map services may generate map service data relying upon variousdata formats separate from a map tile. For example, map services thatprovide location data may utilize data formats conforming to locationservice protocols, such as, but not limited to, Radio Resource Locationservices Protocol (RRLP), TIA 801 for Code Division Multiple Access(CDMA), Radio Resource Control (RRC) position protocol, or LTEPositioning Protocol (LPP). Embodiments may also receive or request datafrom client devices identifying device capabilities or attributes (e.g.,hardware specifications or operating system version) or communicationcapabilities (e.g., device communication bandwidth as determined bywireless signal strength or wire or wireless network type).

A map service may obtain map service data from internal or externalsources. For example, satellite imagery used in map image data may beobtained from external services, or internal systems, storage devices,or nodes. Other examples may include, but are not limited to, GPSassistance servers, wireless network coverage databases, business orpersonal directories, weather data, government information (e.g.,construction updates or road name changes), or traffic reports. Someembodiments of a map service may update map service data (e.g., wirelessnetwork coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client devicerequests for map services. These requests may be a request for aspecific map or portion of a map. Embodiments may format requests for amap as requests for certain map tiles. In some embodiments, requests mayalso supply the map service with starting locations (or currentlocations) and destination locations for a route calculation. A clientdevice may also request map service rendering information, such as maptextures or stylesheets. In at least some embodiments, requests may alsobe one of a series of requests implementing turn-by-turn navigation.Requests for other geographic data may include, but are not limited to,current location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

A map service may, in some embodiments, may analyze client devicerequests to optimize a device or map service operation. For example, amap service may recognize that the location of a client device is in anarea of poor communications (e.g., weak wireless signal) and send moremap service data to supply a client device in the event of loss incommunication or send instructions to utilize different client hardware(e.g., orientation sensors) or software (e.g., utilize wireless locationservices or Wi-Fi positioning instead of GPS-based services). In anotherexample, a map service may analyze a client device request forvector-based map image data and determine that raster-based map databetter optimizes the map image data according to the image's complexity.Embodiments of other map services may perform similar analysis on clientdevice requests and as such the above examples are not intended to belimiting.

Various embodiments of client devices (e.g., client devices 102 a-102 c)may be implemented on different device types. Examples of aportable-multifunction device include the devices illustrated in FIGS. 8through 11, such as multifunction device 1200 and multifunction device1400. Client devices 102 a-102 c may utilize map service 130 throughvarious communication methods and protocols described below. In someembodiments, client devices 102 a-102 c may obtain map service data frommap service 130. Client devices 102 a-102 c may request or receive mapservice data. Client devices 102 a-102 c may then process map servicedata (e.g., render and/or display the data) and may send the data toanother software or hardware module on the device or to an externaldevice or system.

A client device may, according to some embodiments, implement techniquesto render and/or display maps. These maps may be requested or receivedin various formats, such as map tiles described above. A client devicemay render a map in two-dimensional or three-dimensional views. Someembodiments of a client device may display a rendered map and allow auser, system, or device providing input to manipulate a virtual camerain the map, changing the map display according to the virtual camera'sposition, orientation, and field-of-view. Various forms and inputdevices may be implemented to manipulate a virtual camera. In someembodiments, touch input, through certain single or combination gestures(e.g., touch-and-hold or a swipe) may manipulate the virtual camera.Other embodiments may allow manipulation of the device's physicallocation to manipulate a virtual camera. For example, a client devicemay be tilted up from its current position to manipulate the virtualcamera to rotate up. In another example, a client device may be tiltedforward from its current position to move the virtual camera forward.Other input devices to the client device may be implemented including,but not limited to, auditory input (e.g., spoken words), a physicalkeyboard, mouse, and/or a joystick.

A client device may, in some embodiments, provide various visualfeedback to virtual camera manipulations, such as displaying ananimation of possible virtual camera manipulations when transitioningfrom two-dimensional map views to three-dimensional map views. A clientdevice may also allow input to select a map feature or object (e.g., abuilding) and highlight the object, producing a blur effect thatmaintains the virtual camera's perception of three-dimensional space.

In some embodiments, a client device may implement a navigation system(e.g., turn-by-turn navigation). A navigation system provides directionsor route information, which may be displayed to a user. Embodiments of aclient device may request directions or a route calculation from a mapservice. A client device may receive map image data and route data froma map service. In some embodiments, a client device may implement aturn-by-turn navigation system, which provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as Global Positioning Satellite (GPS). A client device may displaymap image data that reflects the current location of the client deviceand update the map image data in real-time. A navigation system mayprovide auditory or visual directions to follow a certain route.

A virtual camera may be implemented to manipulate navigation map dataaccording to some embodiments. Some embodiments of client devices mayallow the device to adjust the virtual camera display orientation tobias toward the route destination. Embodiments may also allow virtualcamera to navigation turns simulating the inertial motion of the virtualcamera.

Client devices may implement various techniques to utilize map servicedata from map service. Embodiments may implement some techniques tooptimize rendering of two-dimensional and three-dimensional map imagedata. In some embodiments, a client device may locally store renderinginformation. For example, a client may store a stylesheet which providesrendering directions for image data containing style identifiers. Inanother example, common image textures may be stored to decrease theamount of map image data transferred from a map service. In a furtherexample, noise texture elements, such as texture elements generatedbased on perlin noise, value noise, or simplex noise may be stored ondevices. Client devices may also dynamically generate map textures basedon texture definitions received from a map service. Client devices mayalso implement various modeling techniques to render two-dimensional andthree-dimensional map image data, examples of which include, but are notlimited to: generating three-dimensional buildings out oftwo-dimensional building footprint data; modeling two-dimensional andthree-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data. Some embodiments ofclient devices may also order or prioritize map service data in certaintechniques. For example, a client device may detect the motion orvelocity of a virtual camera, which if exceeding certain thresholdvalues, lower-detail image data will be loaded and rendered of certainareas. Other examples include: rendering vector-based curves as a seriesof points, preloading map image data for areas of poor communicationwith a map service, adapting textures based on display zoom level, orrendering map image data according to complexity.

In some embodiments, client devices may communicate utilizing variousdata formats separate from a map tile. For example, some client devicesmay implement Assisted Global Positioning Satellites (A-GPS) andcommunicate with location services that utilize data formats conformingto location service protocols, such as, but not limited to, RadioResource Location services Protocol (RRLP), TIA 801 for Code DivisionMultiple Access (CDMA), Radio Resource Control (RRC) position protocol,or LTE Positioning Protocol (LPP). Client devices may also receive GPSsignals directly. Embodiments may also send data, with or withoutsolicitation from a map service, identifying the client device'scapabilities or attributes (e.g., hardware specifications or operatingsystem version) or communication capabilities (e.g., devicecommunication bandwidth as determined by wireless signal strength orwire or wireless network type).

FIG. 1 illustrates one possible embodiment of an operating environment100 for a map service 130 and client devices 102 a-102 c. In someembodiments, devices 102 a, 102 b, and 102 c can communicate over one ormore wire or wireless networks 110. For example, wireless network 110,such as a cellular network, can communicate with a wide area network(WAN) 120, such as the Internet, by use of gateway 114. A gateway 114may provide a packet oriented mobile data service, such as GeneralPacket Radio Service (GPRS), or other mobile data service allowingwireless networks to transmit data to other networks, such as wide areanetwork 120. Likewise, access device 112 (e.g., IEEE 802.11g wirelessaccess device) can provide communication access to WAN 120. Devices 102a and 102 b can be any portable electronic or computing device capableof communicating with a map service, such as a portable multifunctiondevice described below with respect to FIGS. 5 to 8. Device 402 c can beany non-portable electronic or computing device capable of communicatingwith a map service, such as a system described below in FIG. 9.

In some embodiments, both voice and data communications can beestablished over wireless network 110 and access device 112. Forexample, device 102 a can place and receive phone calls (e.g., usingvoice over Internet Protocol (VoIP) protocols), send and receive e-mailmessages (e.g., using Simple Mail Transfer Protocol (SMTP) or PostOffice Protocol 3 (POP3)), and retrieve electronic documents and/orstreams, such as web pages, photographs, and videos, over wirelessnetwork 110, gateway 114, and WAN 120 (e.g., using Transmission ControlProtocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)).Likewise, in some implementations, devices 102 b and 102 c can place andreceive phone calls, send and receive e-mail messages, and retrieveelectronic documents over access device 112 and WAN 120. In variousembodiments, any of the illustrated client device may communicate withmap service 130 and/or other service(s) 150 using a persistentconnection established in accordance with one or more securityprotocols, such as the Secure Sockets Layer (SSL) protocol or theTransport Layer Security (TLS) protocol.

Devices 102 a and 102 b can also establish communications by othermeans. For example, wireless device 102 a can communicate with otherwireless devices (e.g., other devices 102 a or 102 b, cell phones) overthe wireless network 110. Likewise devices 102 a and 102 b can establishpeer-to-peer communications 140 (e.g., a personal area network) by useof one or more communication subsystems, such as Bluetooth®communication from Bluetooth Special Interest Group, Inc. of Kirkland,Wash. 102 c can also establish peer to peer communications with devices102 a or 102 b. (not pictured). Other communication protocols andtopologies can also be implemented. Devices 102 a and 102 b may alsoreceive Global Positioning Satellite (GPS) signals from GPS 140.

Devices 102 a, 102 b, and 102 c can communicate with map service 130over the one or more wire and/or wireless networks, 110 or 112. Forexample, map service 130 can provide a map service data to renderingdevices 102 a, 102 b, and 102 c. Map service 130 may also communicatewith other services 150 to obtain data to implement map services. Mapservice 130 and other services 150 may also receive GPS signals from GPS140.

In various embodiments, map service 130 and/or other service(s) 150 maybe configured to process search requests from any of client devices.Search requests may include but are not limited to queries for business,address, residential locations, points of interest, or some combinationthereof. Map service 130 and/or other service(s) 150 may be configuredto return results related to a variety of parameters including but notlimited to a location entered into an address bar or other text entryfield (including abbreviations and/or other shorthand notation), acurrent map view (e.g., user may be viewing one location on themultifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriainclude but not limited to a quantity of times the search result (e.g.,a particular point of interest) has been requested, a measure of qualityassociated with the search result (e.g., highest user or editorialreview rating), and/or the volume of reviews for the search results(e.g., the number of times the search result has been review or rated).

In various embodiments, map service 130 and/or other service(s) 150 maybe configured to provide auto-complete search results that may bedisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the internet) by map service 130 and/or other service(s) 150,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device may be configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 130 and/or other service(s) 150 mayprovide one or more feedback mechanisms to receive feedback from clientdevices 102 a-c. For instance, client devices may provide feedback onsearch results to map service 130 and/or other service(s) 150 (e.g.,feedback specifying ratings, reviews, temporary or permanent businessclosures, errors etc.); this feedback may be used to update informationabout points of interest in order to provide more accurate or moreup-to-date search results in the future. In some embodiments, mapservice 130 and/or other service(s) 150 may provide testing informationto the client device (e.g., an A/B test) to determine which searchresults are best. For instance, at random intervals, the client devicemay receive and present two search results to a user and allow the userto indicate the best result. The client device may report the testresults to map service 130 and/or other service(s) 150 to improve futuresearch results based on the chosen testing technique, such as an A/Btest technique in which a baseline control sample is compared to avariety of single-variable test samples in order to improve results.

Workflow Overview for Dynamically Generating Map Textures

Dynamically generating map textures may be implemented in differentways. According to various embodiments, FIG. 2 illustrates a high-levelflowchart of one implementation of a method of dynamically generatingmap textures. A computing or electronic device capable of renderingimages, such as map views based on map data, with textures may, forexample may be a desktop computer, a notebook or laptop computer, aclient device, such as client device 102 described above with respect toFIG. 1, a portable multi-function device, such as described below withregard to FIGS. 5 through 8, a system, such as described below at FIG.9, or in general any computing device capable of obtaining and renderingmap data.

Various embodiments may obtain map data 210 from a server, such as mapservice 130 described with regard to FIG. 1. Transport of the map datafrom a server may occur through one or more of the many communicationchannels discussed above with regard to FIG. 1, such as a wide areanetwork like the Internet 120 and wired or wireless communicationssignals. Obtained map data may be two-dimensional or three-dimensional.The obtained map data may contain vector graphics data which describesone or more shapes. Vector graphics data may be encoded using vectorgraphic formats, including, but not limited to, Scalable Vector Graphics(.svg) or a Drawing File (.drw). Map data may also be composed of one ormore map tiles, also described above with respect to FIG. 1, which areportions of a map which may be reassembled to display the map. In someembodiments, map data may also include texture identifiers linked to theone or more shapes described by the obtained map data. In addition tothe shapes described by vector graphics data, some embodiments mayobtain map data that contains one or more areas distinct from theshapes. These areas may be described using other graphics formats, suchas raster graphics data. Areas may also include vector graphics datawhich are not linked to texture identifiers.

A client device may, in some embodiments, render a map view based on theobtained map data for display. For one or more of the described shapesfor the map, a client device may obtain a particular texture definitionfor the shape 220. In at least some embodiments, a client device mayobtain the texture definition according to the texture identifier linkedto the shape. A texture identifier may be descriptive of the shape towhich it is linked. For example, a texture identifier may be “AtlanticOcean” and linked to one or more shapes described by the map data that,when rendered, display portions of the Atlantic Ocean. To obtain atexture definition for shapes linked to the “Atlantic Ocean” identifier,a client device may submit a request for a texture definition for the“Atlantic Ocean” to a map service. A map service may respond with thetexture definition, which may include one or more instructions togenerate a texture for the Atlantic Ocean. Many other methods ofobtaining a particular texture definition are further described below,and thus, the previous example is not intended to be limiting.

After obtaining a texture definition for a shape, a client device may,in some embodiments, dynamically generate a texture for the shapeaccording to the particular texture definition for the shape 230.Various implementations of dynamically generating a texture arediscussed below with regard to FIGS. 3A and 3B. In some embodiments,textures may be generated by obtaining locally stored or generated basetexture layers, noise texture elements, or pattern texture elements on aclient device. In some other embodiments, one or more of the basetexture layers, noise texture elements, or pattern texture elements maybe obtained from one or more texture data providers. Texture dataproviders, as discussed below, may be one or more modules, applications,systems, users, or services, such as map service 130 described above inFIG. 1, which provide data to generate a texture. Generated textures,may be, but are not limited to, images which display common or repeatingelements of a map view. For example, a texture may be the grassbackground of a larger park image. However, they may also be largerimages with varied elements. A texture may be applied in two-dimensionaland three-dimensional shapes. Some textures may include a series oftextures to be displayed in sequence to create an animation.

Once a texture is generated for a shape, some embodiments may apply thegenerated texture to the shape to render a current fill portion of theshape 240. A current fill portion may be defined by the shape and may bethe location for a texture to be applied. Various implementations arediscussed below. Many well-known techniques exist to apply textures toshapes and render current fill portions of the shapes. Creating andfilling a shape described by vector graphics, for example, may beaccomplished using various techniques and implementations well-known tothose of ordinary skill in the art. Embodiments may implement commontechniques which are platform independent, such as, but not limited to,utilizing the Open Graphics Library (OpenGL) or Direct3D applicationprogrammer interfaces, or variants thereof such as OpenGL ES. Customizedrendering applications which may optimize the performance of CPUs orGPUs may also be implemented. Numerous other configurations of hardwareand software may also be implemented to apply textures to render fillportions of shapes, and therefore, the previous examples are notintended to be limiting.

Upon completion of rendering the map view based on the obtained mapdata, a client device may, in some embodiments, display the rendered mapview 250 based upon the map data. For example, a client device, such asthe portable multifunction device 1000 described below with regard toFIGS. 5 through 8, may display the map view on a display located on theclient device (e.g., touch-sensitive display 1012 in FIG. 7). A clientdevice may also store the rendered map view or send the map view toother modules or applications for further processing.

Obtaining Texture Definitions

A client device, such as client device 102 described above in FIG. 1,may dynamically generate textures for one or more shapes described bymap data received at the client device. As indicated at 230 in FIG. 2,textures may be generated according to a particular texture definition.Particular texture definitions may be obtained from a variety of sourceslocated locally at the client device or remotely on other systems.

In various embodiments, a client device may receive, along with mapdata, texture identifiers. Texture identifiers may be a numeric, string,or other symbolic value which may be used to obtain a texturedefinition. In some embodiments, a texture identifier may be an indexvalue used, for example, in a look up table or other data structure orschema that provides a texture definition that corresponds to thetexture identifier. In some other embodiments, a texture identifier maybe a descriptive tag that a client device or map service, may parse todetermine which texture definition best corresponds to the textureidentifier. For example, a texture identifier linked to a shape may be“golf course.” A client device, map service, or other module orapplication that may provide texture definitions may be configured toparse the texture identifier “golf course” to determine that the “grass”texture definition will be used to generate textures for shapes linkedto “golf course” relying upon various well-known techniques for ranking,rating, and/or determining a best match from among a set of possiblematching texture definitions.

Multiple texture identifiers may be linked to a single map shape, in atleast some embodiments. For example, a shape may be linked to both a“forest” texture identifier and a “U.S. national park” identifier. Aclient device, map service, or other module or application that mayprovide texture definitions may be configured to determine whether atexture definition corresponding to “forest,” a texture definitioncorresponding to “U.S. national park,” or some combination of thetexture definitions are to be provided to a client device. Varioushierarchal schemes may be implemented to obtain a texture definitionbased on one or more texture identifiers linked to a shape, includingparent-child relationships between identifiers or classes and subclassesof texture identifiers. Texture identifiers may be standardized in anApplication Programmer Interface (API) or some other form of previouslydetermined set of approved values and meanings for texture identifiers.In some embodiments, texture identifiers may also be non-standardized orself-defining for embodiments of a texture provider configured todetermine a best match texture definition.

In some other embodiments, each shape may be linked to a single textureidentifier. Further embodiments may also include some shapes linked tothe same texture identifier, such as two shapes both linked to the“park” texture identifier. Various combinations of shapes linked to oneor more texture identifiers may be included in map data obtained at theclient device.

In some embodiments, in order to obtain the texture definition for ashape linked to a particular texture identifier, a client device, forinstance, may submit a request for a texture definition to a map servicethat includes the texture identifier. In return, the map service mayrespond with a texture definition that corresponds to the textureidentifier. For example, a client device may receive a shape linked to a“lake” texture identifier. The client device may then request a texturedefinition for the “lake” texture identifier from a map service, such asmap service 130 described above. In some embodiments, a map service orother service, system, module, or device external to the client devicemay send or push a texture definition to a client device. A clientdevice may also obtain texture definitions from local storage, such as aset of one or more previously obtained texture definitions.

Various components on a client device, such as texture generationcomponent 434 described below with regard to FIG. 4, may parse,decompress, decrypt or otherwise transform into a format understood atthe client device texture definitions that may be transmitted accordingto various security and other transportation protocols, containers, orschemes. Likewise, a texture generation component may construct atexture definition for generating a texture based on indications,information, or input from a variety of sources, such as those describedbelow in FIG. 4.

Blending Texture Layers and Texture Elements

As discussed above with regard to FIG. 2, a client device, such asclient device 102 described above in FIG. 1, may obtain map data, asindicated at 210, describing one or more shapes. A client device maythen wish to render a map view of the map data for display. For one ormore shapes, a client device may obtain a particular texture definition,as indicated at 220. A client device may then dynamically generate atexture for the shape according to the particular texture definition230. In some embodiments, dynamically generating a texture may includeblending a base texture layer with one or more noise texture elements orpattern texture elements. FIG. 3 illustrates a high-level flowchart of amethod of blending texture layers and elements to generate a texture,according to some embodiments.

As indicated at 310, a client device may obtain a base texture layeraccording to the texture definition. A base texture layer may be anytexture information that provides a base or background for a texture. Insome embodiments, the base texture layer is a color value. A texturespecification may, for example, specify the base texture layer as an RGBcolor space value. However, other color space values or colordefinitions may be used, and thus, the above example is not intended tobe limiting. In some other embodiments, a base texture layer may be animage or other portion of graphics data, such as raster graphics datarepresented by a bitmap. A texture definition may provide a location, ora portion or all of the graphics data specified to be the base texturelayer. This graphics data may be a small portion of data that is tiled,or repeatedly joined together to form a larger image. However, in someembodiments the base texture layer may be a single portion of graphicsdata.

To obtain a base texture layer, a client device may access localstorage, such as texture storage 432 described below in FIG. 4. In atleast some embodiments, the base texture layer may be requested andreceived from a map service, or other module, service, or input, such asthose described in FIG. 4. A base texture layer may also be generated bythe client device. For example, if the texture definition specifies acolor value, the client device may generate a base texture layer of thatcolor value. Likewise, if a texture definition specifies a portion ofgraphics data that is to be tiled, a client device may repeatedly jointhe portion of graphics data together in order to generate the basetexture layer.

In some embodiments, a client device may also obtain noise textureelements or pattern texture elements according to the texturedefinition. A noise texture element may be a graphics primitive orelement generated according to one of a variety of well-known noisetexture algorithms, such as perlin noise, value noise, or simplex noise.Those with ordinary skill in the art will recognize that numerousmethods of generating noise texture elements are well-known, and thusthe above list of noise elements is not intended to be limiting. A noisetexture element may provide a random or pseudo-random element to beblended with a base texture layer and possibly one or more other textureelements, easily providing an endless variety of different generatedtextures. Noise texture elements may be generated on the client device,such as by noise texture generator 438 described in FIG. 4 below, orobtained from a map service or other services, modules, systems,devices, or inputs. Noise texture elements may be stored locally on theclient device, such as in texture storage 432, or remotely, such as on amap service.

A texture definition may specify a particular noise texture element tobe used when generating a texture. For example, a texture definition mayprovide an index value, name, or other identifier that allows a clientto look up a locally stored noise texture element or request a noisetexture element from another remote location. A texture definition mayalso provide instructions for a particular noise texture element to begenerated by the client device, such as providing specific inputs to anose texture generation algorithm.

In some embodiments, a texture definition may specify a pattern textureelement to be obtained for use in generating a texture. A patterntexture element may be a graphics primitive or element that conveysgraphical information through a pattern. For example, a pattern textureelement may be a pattern of contour lines indicating elevation changes.In another example, a pattern texture element may mask or crop certainportions of a texture from being blended with one or more other texturelayers or elements. Pattern texture elements may be store locally on aclient device, generated on a client device, or obtain from a remotelocation, such as a map service or other service, module, system,device, or input. A texture definition may specify a particular patterntexture element by providing an index value, location, or generationinstructions to a client device.

Upon obtaining the base texture layer 310 and the one noise textureelements and/or pattern texture elements 320, a client device may, insome embodiments, combine the base texture layer with the one or morenoise texture elements or pattern textures elements 330 to generate thetexture for the shape. FIG. 3B illustrates the combination of texturelayers and elements, according to some embodiments. A client device mayblend a base texture layer 360 with a noise texture element 370 and/or apattern texture element 380 to generate a texture. For example, basetexture layer 360 may be specified by a texture definition as particularblue color value. Noise texture element 370 may be specified as aparticular noise texture element store at the client device thatresembles moving water. Pattern texture element 380 may provide patternsof depth information. A blending component, such as layer blendingcomponent 436 described below with regard to FIG. 4, may combine thesethree layers to generate an ocean texture that displays depthinformation. Note, that a nearly infinite number of possiblecombinations of base layers with noise texture elements and patterntexture elements exist, and therefore, the previous illustration andexample is not intended to be limiting.

Many graphics blending techniques may be implemented to blend betweenthe base texture layer and one or more noise texture elements and/orpattern texture elements. Each layer or texture element may adjust,manipulate, and/or transform any number of graphical values ofsurrounding layers or texture elements, including, but not limited,color, contrast, brightness, alpha, sharpness, intensity, frequency,hue, saturation, tint, lightness, or other graphical value or graphicaloperation. Graphics techniques and operations for manipulating thepreviously listed values are well-known to those of ordinary skill inthe art, and therefore, the previous list is not intended to belimiting. For example, one texture element may operate as an alphamatte, while another texture element may adjust hue. Use of thesevarious graphic values may simulate many different textures, such asvarying geographic landcovers specific to one or more locations in amap, as well as provide the flexibility to create seasonal or otheron-the-fly contextual changes in a map view by adjusting one or moretexture definitions used to generate textures for shapes in a map view.A texture definition may provide specific blending instructions to alayer blending component concerning the base texture layers and textureelements, including, but not limited to, opacity values, multiply,screen, overlay, darken, lighten, color dodge, color burn, soft light,hard light, difference, exclusion, hue, saturation, color, luminosity,clear, copy, source manipulations, destination manipulations, and xor,to manipulate graphical values and perform graphical operations at theclient device.

In some embodiments, in addition to the texture definition, a texturemay be generated based upon texture data received from one or moretexture data providers. Texture data providers may be one or moremodules, applications, systems, users, or services, which provide datato generate a texture. For example, a texture generation component mayreceive texture data from a traffic service. The traffic service maycommunicate with the function using one of the communication channelsdiscussed above with regard to FIG. 1. The texture generation functionmay be given as input a texture definition for a road which it willcombine with the texture traffic data for that road. The texture datafor the road reflecting the traffic may then be returned to be appliedto generate a unique texture that conveys traffic information applied tothe road shape. The generating function or component may interact withvarious other modules, systems, users, or services to providecontextualized textures.

Dynamically generated textures are generally graphical data that may beapplied to other graphical data. The various forms of graphics data,such as raster graphics data, discussed above may be implemented astextures. In some embodiments a texture may be constructed from adynamically generated image tile that is copied and combined with itselfrepeatedly in order to generate a larger texture image of a desiredsize. Texture image tiles are commonly, but not limited to, 8×8 pixels.However this size may be adjusted larger or smaller to incorporate moreor less detail in a texture. Dynamically generated textures may also beimplemented as mipmaps, where different sized textures are provided to arendering device dependent on the zoom level of the textured map data.Embodiments may store generated textures on the device, such as intexture storage 432 in FIG. 4. In some embodiments, a texture may beobtained from another external system or device, such as an image serveror a map service 130, or be obtained from a source internal to thedevice or system, such as another application, module or hardwaredevice. For example, in some embodiments a texture may be generatedusing a graphics editor stored on the device or by capturing a textureutilizing an onboard camera.

As indicated at 340, dynamically generated textures may be applied toone or more of the describe shapes obtained in the map data. Asdiscussed above with regard to FIG. 2, a rendered map view may bedisplayed, stored, or sent to other modules or systems for furtherprocessing.

Varying Dynamically Generated Textures

In some embodiments, many possible implementations exist to vary thedynamically generated texture to render a current fill portion of one ormore shapes. For example, in some embodiments, a client device mayreceive an indication of a particular event (e.g., time, location, zoomlevel, map view mode, etc. . . . ). In response the client device mayvary the current fill portion of one or more shapes in the map data. Insome embodiments, a client device may receive a push notification orchange notification of a particular change to a texture definition andautomatically vary the current filled portion of the affected shapesaccordingly. In some embodiments, a texture definition may include asequence of texture specifications that cause a client device togenerate a sequence of textures that render a texture animation for thecurrent fill portion of a shape. In at least some embodiments, a clientdevice that obtains map data with shapes linked to the same textureidentifier may vary the textures in order to generate different texturesfor the shapes.

In some embodiments a client device may be configured to maintain acurrent time value for the client device, such as the clock widgetindicated at 1049-4 in FIG. 10. A texture definition, such as discussedabove with regard to FIGS. 2 and 3A, a map data rendering module, suchas indicated at 420 in FIG. 4, a map module, such as indicated at 400 inFIG. 4, client device module or application, or a map service, such asindicated at 130 in FIG. 1, may provide instructions to a client devicethat at a particular event, such as a particular time, one or moretexture definitions for map data may change. In response, a clientdevice may vary a current fill portion of one or more shapes bydynamically generating another texture for the shape according to thechanged texture definition and applying the generated other texture tothe shape to render the current fill portion of the shape. For example,a client device may receive an indication that it is 6:30 p.m. on theclient device. In response, the client device may obtain one or morechanged texture definitions that change base texture layer color valuesto create a “sunset” effect. Textures may be dynamically generated basedon the new base texture layer color values and applied to one or moreshapes. This process may be repeated at multiple intervals to create aslow animation effect. In some other embodiments, a client device mayobtain a new texture definition to be used instead of the previouslyused texture definition. Or, in some embodiments a previously storedtexture may be used to render current fill portions for one or moreshapes.

In some embodiments a client device may be configured to maintain acurrent location for the client device, such as the GPS module indicatedat 1035 in FIG. 10. A texture definition, such as discussed above withregard to FIGS. 2 and 3A, a map data rendering module, such as indicatedat 420 in FIG. 4, a map module, such as indicated at 400 in FIG. 4,client device module or application, or a map service, such as indicatedat 130 in FIG. 1, may provide instructions to a client device that at aparticular event, such as a particular location, one or more texturedefinitions for map data may change. In response, a client device mayvary a current fill portion of one or more shapes by dynamicallygenerating another texture for the shape according to the changedtexture definition and applying the generated other texture to the shapeto render the current fill portion of the shape. For example, a clientdevice may receive an indication that it is now located in Germany onthe client device. In response, the client device may obtain one or morechanged texture definitions that change base texture layer noise elementtextures to draw the distinctive landscape features of Germany. Texturesmay be dynamically generated based on the new noise texture elements andapplied to one or more shapes. In some other embodiments, a clientdevice may obtain a new texture definition to be used instead of thepreviously used texture definition. Or, in some embodiments a previouslystored texture may be used to render current fill portions for one ormore shapes.

In some embodiments a client device may be configured to display a mapview at varying zoom levels. A texture definition, such as discussedabove with regard to FIGS. 2 and 3A, a map data rendering module, suchas indicated at 420 in FIG. 4, a map module, such as indicated at 400 inFIG. 4, client device module or application, or a map service, such asindicated at 130 in FIG. 1, may provide instructions to a client devicethat at a particular event, such as at a particular zoom level, one ormore texture definitions for map data may change. In response, a clientdevice may vary a current fill portion of one or more shapes byobtaining a second texture definition texture for the shape according tothe indicated zoom level, dynamically generating another texture for theshape according to the second texture definition and applying thegenerated other texture to the shape to render the current fill portionof the shape. For example, a client device may receive an indicationthat it is at zoom level 15, simulating a 1500 foot aerial map view onthe client device. In response, the client device may obtain one or morechanged texture definitions that a replace a previously specified noisetexture element with another noise texture element to illustrate thefewer details of landscape shown at a greater map view height. Texturesmay be dynamically generated based on the new base texture layer colorvalues and applied to one or more shapes. In some other embodiments, aclient device may obtain a new texture definition to be used instead ofthe previously used texture definition. Or, in some embodiments apreviously store texture may be used to render current fill portions forone or more shapes.

In some embodiments a client device may be configured to display a mapview in different map view modes. A map view mode may be a displayscheme that displays map data in a particular format. For example, anight view mode may display some landcover as much darker than would bedisplayed in day mode. Likewise, a pedestrian map view mode may behighlight pedestrian only routes. A texture definition, such asdiscussed above with regard to FIGS. 2 and 3A, a map data renderingmodule, such as indicated at 420 in FIG. 4, a map module, such asindicated at 400 in FIG. 4, client device module or application, or amap service, such as indicated at 130 in FIG. 1, may provideinstructions to a client device that at a particular event, such as at aparticular map view mode, one or more texture definitions for map datamay change. In response, a client device may vary a current fill portionof one or more shapes by obtaining a second texture definition accordingto the indicated map view mode, dynamically generating another texturefor the shape according to the second texture definition and applyingthe generated other texture to the shape to render the current fillportion of the shape. For example, a client device may receive anindication that it is at night map view mode on the client device, suchas by user selection or an ambient light sensor on the client device. Inresponse, the client device may obtain one or more changed texturedefinitions that a replace a previously specified base texture layercolor value with another darker base texture layer color value toillustrate the change to nigh mode. Textures may be dynamicallygenerated based on the new base texture layer color values and appliedto one or more shapes. In some other embodiments, a client device mayobtain a new texture definition to be used instead of the previouslyused texture definition. Or, in some embodiments a previously storedtexture may be used to render current fill portions for one or moreshapes.

A texture definition, in some embodiments, may include a sequence oftexture specifications. When a client device generates a textureaccording to such a texture definition, a sequence of textures for theshape may be generated to render a texture animation. For instance, atexture definition for a shape defining an ocean texture may include asequence of ocean texture specifications. When the ocean texture isdynamically generated according to the texture definition, thesedifferent textures may be generated and stored in storage location. Aclient device may then display the map view with the one or more shapesfilled by the ocean texture, display in succession the sequence of oceantextures displaying a texture animation. This animation may be repeatedover varying intervals or displayed only once. A texture animation may,in combination with other indications occur at the indication of variousevents. For example, when the current time is indicated to be at thetime for high tide, the ocean texture may animate a rise in ocean level.Or, in another example the color palette of a map view may slowlytransition from day mode to night mode as the current time indicatedchanges from daylight time to night time. Numerous other textureanimation implementations may be devised, and as such, the previousexamples are not to be construed as limiting.

In some embodiments, the map data may describe two or more shapes linkedto the same texture identifier. A client device may be configured tovary the textures dynamically generated for the two shapes. A clientdevice may vary one or more of the base texture layers, noise textureelements, or pattern texture elements. A client device may also vary theblending instructions between layers and texture elements. A clientdevice may determine which shape's texture to vary based upondeterminate methods, such as the proximity of the shapes to one another,or the proximity of all shapes in the map view. For example, if in acity map two shapes linked to a “park” texture identifier are within 10miles of one another, a client device may vary the noise texture elementof one of the shapes so as to generate a different park texture thatappears to have different foliage or landscape. Alternatively, in someembodiments, a client device may randomly determine which shape'stexture to vary. For example, if in an aerial map view multiple shapesare linked to a “field” texture identifier, a client device may randomlyvary the base texture layer color of shapes to create a “patchwork”field effect. As the possible combinations of varying dynamicallygenerated textures by varying the base texture layers or textureelements are very large, the previous examples may not be construed aslimiting.

Example Embodiments

Various embodiments may implement a method of dynamically generating maptextures. An electronic device or portable multifunction device, such asdescribed below with respect to FIGS. 5 through 8 below, or a system,such as described below with regard to FIG. 9. A map module may, in someembodiments, be implemented by a non-transitory, computer-readablestorage medium and one or more processors (e.g., CPUs and/or GPUs) of acomputing apparatus. The computer-readable storage medium may storeprogram instructions executable by the one or more processors to causethe computing apparatus to implement: obtaining from a server, by a mapapplication, map data, wherein said map data comprises vector graphicsdata describing one or more shapes for a map; rendering a map view basedon the obtained map data for display on the computing device comprising:for one or more of the shapes described for the map: obtaining aparticular texture definition for the shape; dynamically generating atexture for the shape according to the particular texture definition;and applying the generated texture to the shape to render a current fillportion of the shape. Other embodiments of the map module may be atleast partially implemented by hardware circuitry and/or firmwarestored, for example, in a non-volatile memory.

FIG. 4 illustrates a map module that implements dynamically generatingmap textures as described with regard to FIGS. 2 and 3. FIG. 4 is onlyan example of a module and is not intended to be limiting as to thisexample or other categories of applications that may implement renderingimages with texture masks. A map service 410, such as a map service 130described in FIG. 1, may generate map data. The map module 400 mayrequest or receive map data from the map service 410. The map service410 may also provide texture identifiers, texture definitions, texturelayers, or texture elements to a texture generation component 434. Themap service may also supply texture definitions, texture layers, ortexture elements to the texture storage 432, such as memory 1002 in FIG.5.

A map data rendering module 420 may obtain a map data with vectorgraphics describing one or more shapes and with corresponding maskindicators from the map service 410. The map data rendering module 420may render a map view based on the obtained map data for display. Forone of more of the described shapes map rendering module 420 may requesta texture from the texture generation component 434. The texturegeneration component may obtain texture definitions from the map service410, based on texture identifiers from the map service 410, texturestorage 432, or other services 416, or other modules 414. In addition tothe texture definition, texture generation component 434 may also obtaintexture data from other services 416. For example, a weather service maysubmit weather texture data to render clouds or radar data. Texture datamay also be non-graphic data. For example, the weather service mayprovide current weather data to the texture generation component 434which provides information that certain areas in the map were verywindy. The texture generation component 434 may dynamically generate atexture for a shape according to a texture definition. A layer blendingcomponent 436 may blend a base texture layer and one or more noisetexture elements or pattern texture elements. In some embodiments, atexture definition may require a noise texture element to be generatedutilizing a noise texture generator 438. Texture generation component434 may also obtain other texture data from other modules/applicationson an implementing device. For example, modules may provide additionalannotations to map data, such as a sea navigation module that mayprovide various textures to a map for bodies of water that representvarying levels of water depth. Texture generation component 434 may alsoobtain texture data from user input 412. For example, a user may be ableto set up certain display preferences or display modes, such as aselection of night mode for a map.

Once the requested textures are dynamically generated for shapes shape,the map data rendering module 420 may apply the dynamically generatedtextures to the one or more shapes to render a current fill portion forthe shape. The map module 700 may then send the rendered map view to adisplay 460, located on the device, such as touch-sensitive display 1012in FIG. 10, or a display on another device or system. The rendered mapview may also be sent to other modules 450 on the device for furtherprocessing. The map rendering module 400 may also send the rendered mapimage to a storage medium 440, located on the client device or anothersystem or device.

Other various implementations of the map module described above mayimplement methods of dynamically generating map textures. Therefore, theabove example is not intended to be limiting.

Example Electronic Device

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the IPHONE®, IPOD TOUCH®, and IPAD®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the device is a gaming computer withorientation sensors (e.g., orientation sensors in a gaming controller).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 5 is a block diagram illustratingportable multifunction device 1000 with touch-sensitive displays 1012 inaccordance with some embodiments. Touch-sensitive display 1012 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 1000 may includememory 1002 (which may include one or more computer readable storagemediums), memory controller 1022, one or more processing units (CPU's)1020, peripherals interface 1018, RF circuitry 1008, audio circuitry1010, speaker 1011, microphone 1013, input/output (I/O) subsystem 1006,other input or control devices 1016, and external port 1024. Device 1000may include one or more optical sensors 1064. These components maycommunicate over one or more communication buses or signal lines 1003.

It should be appreciated that device 1000 is only one example of aportable multifunction device, and that device 1000 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 5 may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 1002 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 1002 by other components of device 1000, suchas CPU 1020 and the peripherals interface 1018, may be controlled bymemory controller 1022.

Peripherals interface 1018 can be used to couple input and outputperipherals of the device to CPU 1020 and memory 1002. The one or moreprocessors 1020 run or execute various software programs and/or sets ofinstructions stored in memory 1002 to perform various functions fordevice 1000 and to process data.

In some embodiments, peripherals interface 1018, CPU 1020, and memorycontroller 1022 may be implemented on a single chip, such as chip 1004.In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 1008 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 1008 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 1008 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 1008 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of multiple communications standards, protocols and technologies,including but not limited to Global System for Mobile Communications(GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packetaccess (HSDPA), high-speed uplink packet access (HSUPA), wideband codedivision multiple access (W-CDMA), code division multiple access (CDMA),time division multiple access (TDMA), Bluetooth, Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 1010, speaker 1011, and microphone 1013 provide an audiointerface between a user and device 1000. Audio circuitry 1010 receivesaudio data from peripherals interface 1018, converts the audio data toan electrical signal, and transmits the electrical signal to speaker1011. Speaker 1011 converts the electrical signal to human-audible soundwaves. Audio circuitry 1010 also receives electrical signals convertedby microphone 1013 from sound waves. Audio circuitry 1010 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 1018 for processing. Audio data may be retrievedfrom and/or transmitted to memory 1002 and/or RF circuitry 1008 byperipherals interface 1018. In some embodiments, audio circuitry 1010also includes a headset jack (e.g., 1212, FIG. 7). The headset jackprovides an interface between audio circuitry 1010 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 1006 couples input/output peripherals on device 1000, suchas touch screen 1012 and other input control devices 1016, toperipherals interface 1018. I/O subsystem 1006 may include displaycontroller 1056 and one or more input controllers 1060 for other inputor control devices. The one or more input controllers 1060 receive/sendelectrical signals from/to other input or control devices 1016. Theother input control devices 1016 may include physical buttons (e.g.,push buttons, rocker buttons, etc.), dials, slider switches, joysticks,click wheels, and so forth. In some alternate embodiments, inputcontroller(s) 1060 may be coupled to any (or none) of the following: akeyboard, infrared port, USB port, and a pointer device such as a mouse.The one or more buttons (e.g., 1208, FIG. 7) may include an up/downbutton for volume control of speaker 1011 and/or microphone 1013. Theone or more buttons may include a push button (e.g., 1206, FIG. 7).

Touch-sensitive display 1012 provides an input interface and an outputinterface between the device and a user. Display controller 1056receives and/or sends electrical signals from/to touch screen 1012.Touch screen 1012 displays visual output to the user. The visual outputmay include graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output may correspond to user-interface objects.

Touch screen 1012 has a touch-sensitive surface, sensor or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 1012 and display controller 1056 (along with anyassociated modules and/or sets of instructions in memory 1002) detectcontact (and any movement or breaking of the contact) on touch screen1012 and converts the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages orimages) that are displayed on touch screen 1012. In an exemplaryembodiment, a point of contact between touch screen 1012 and the usercorresponds to a finger of the user.

Touch screen 1012 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 1012 and display controller 1056 maydetect contact and any movement or breaking thereof using any ofmultiple touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 1012. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theIPHONE®, IPOD TOUCH®, and IPAD® from Apple Inc. of Cupertino, Calif.

Touch screen 1012 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 1060 dpi. The user may make contact with touch screen 1012using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 1000 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 1012 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 1000 also includes power system 1062 for powering the variouscomponents. Power system 1062 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 1000 may also include one or more optical sensors 1064. FIG. 5shows an optical sensor coupled to optical sensor controller 1058 in I/Osubsystem 1006. Optical sensor 1064 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 1064 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 1043(also called a camera module), optical sensor 1064 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 1000, opposite touch screen display 1012 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image may be obtained for videoconferencingwhile the user views the other video conference participants on thetouch screen display.

Device 1000 may also include one or more proximity sensors 1066. FIG. 5shows proximity sensor 1066 coupled to peripherals interface 1018.Alternately, proximity sensor 1066 may be coupled to input controller1060 in I/O subsystem 1006. In some embodiments, the proximity sensorturns off and disables touch screen 1012 when the multifunction deviceis placed near the user's ear (e.g., when the user is making a phonecall).

Device 1000 includes one or more orientation sensors 1068. In someembodiments, the one or more orientation sensors include one or moreaccelerometers (e.g., one or more linear accelerometers and/or one ormore rotational accelerometers). In some embodiments, the one or moreorientation sensors include one or more gyroscopes. In some embodiments,the one or more orientation sensors include one or more magnetometers.In some embodiments, the one or more orientation sensors include one ormore of global positioning system (GPS), Global Navigation SatelliteSystem (GLONASS), and/or other global navigation system receivers. TheGPS, GLONASS, and/or other global navigation system receivers may beused for obtaining information concerning the location and orientation(e.g., portrait or landscape) of device 1000. In some embodiments, theone or more orientation sensors include any combination oforientation/rotation sensors. FIG. 5 shows the one or more orientationsensors 1068 coupled to peripherals interface 1018. Alternately, the oneor more orientation sensors 1068 may be coupled to an input controller1060 in I/O subsystem 1006. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreorientation sensors.

In some embodiments, the software components stored in memory 1002include operating system 1026, communication module (or set ofinstructions) 1028, contact/motion module (or set of instructions) 1030,graphics module (or set of instructions) 1032, text input module (or setof instructions) 1034, Global Positioning System (GPS) module (or set ofinstructions) 1035, and applications (or sets of instructions) 1036.Furthermore, in some embodiments memory 1002 stores device/globalinternal state 1057, as shown in FIG. 5. Device/global internal state1057 includes one or more of: active application state, indicating whichapplications, if any, are currently active; display state, indicatingwhat applications, views or other information occupy various regions oftouch screen display 1012; sensor state, including information obtainedfrom the device's various sensors and input control devices 1016; andlocation information concerning the device's location and/or attitude.

Operating system 1026 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS,or an embedded operating system such as VxWorks) includes varioussoftware components and/or drivers for controlling and managing generalsystem tasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 1028 facilitates communication with other devicesover one or more external ports 1024 and also includes various softwarecomponents for handling data received by RF circuitry 1008 and/orexternal port 1024. External port 1024 (e.g., Universal Serial Bus(USB), FIREWIRE, etc.) is adapted for coupling directly to other devicesor indirectly over a network (e.g., the Internet, wireless LAN, etc.).In some embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on IPOD (trademark of Apple Inc.) devices.

Contact/motion module 1030 may detect contact with touch screen 1012 (inconjunction with display controller 1056) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 1030 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 1030receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 1030 and display controller 1056detect contact on a touchpad.

Contact/motion module 1030 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 1032 includes various known software components forrendering and displaying graphics on touch screen 1012 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 1032 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 1032 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 1056.

Text input module 1034, which may be a component of graphics module1032, provides soft keyboards for entering text in various applications(e.g., contacts 1037, e-mail 1040, IM 1041, browser 1047, and any otherapplication that needs text input).

GPS module 1035 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 1038 foruse in location-based dialing, to camera 1043 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 1036 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 1037 (sometimes called an address book or        contact list);    -   telephone module 1038;    -   video conferencing module 1039;    -   e-mail client module 1040;    -   instant messaging (IM) module 1041;    -   workout support module 1042;    -   camera module 1043 for still and/or video images;    -   image management module 1044;    -   browser module 1047;    -   calendar module 1048;    -   widget modules 1049, which may include one or more of: weather        widget 1049-1, stocks widget 1049-2, calculator widget 1049-3,        alarm clock widget 1049-4, dictionary widget 1049-5, and other        widgets obtained by the user, as well as user-created widgets        1049-6;    -   widget creator module 1050 for making user-created widgets        1049-6;    -   search module 1051;    -   video and music player module 1052, which may be made up of a        video player    -   module and a music player module;    -   notes module 1053;    -   map module 1054; and/or    -   online video module 1055.

Examples of other applications 1036 that may be stored in memory 1002include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 1012, display controller 1056, contactmodule 1030, graphics module 1032, and text input module 1034, contactsmodule 1037 may be used to manage an address book or contact list (e.g.,stored in application internal state 1092 of contacts module 1037 inmemory 1002), including: adding name(s) to the address book; deletingname(s) from the address book; associating telephone number(s), e-mailaddress(es), physical address(es) or other information with a name;associating an image with a name; categorizing and sorting names;providing telephone numbers or e-mail addresses to initiate and/orfacilitate communications by telephone 1038, video conference 1039,e-mail 1040, or IM 1041; and so forth.

In conjunction with RF circuitry 1008, audio circuitry 1010, speaker1011, microphone 1013, touch screen 1012, display controller 1056,contact module 1030, graphics module 1032, and text input module 1034,telephone module 1038 may be used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 1037, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication may use any of multiple communicationsstandards, protocols and technologies.

In conjunction with RF circuitry 1008, audio circuitry 1010, speaker1011, microphone 1013, touch screen 1012, display controller 1056,optical sensor 1064, optical sensor controller 1058, contact module1030, graphics module 1032, text input module 1034, contact list 1037,and telephone module 1038, videoconferencing module 1039 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 1008, touch screen 1012, displaycontroller 1056, contact module 1030, graphics module 1032, and textinput module 1034, e-mail client module 1040 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 1044,e-mail client module 1040 makes it very easy to create and send e-mailswith still or video images taken with camera module 1043.

In conjunction with RF circuitry 1008, touch screen 1012, displaycontroller 1056, contact module 1030, graphics module 1032, and textinput module 1034, the instant messaging module 1041 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 1008, touch screen 1012, displaycontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, GPS module 1035, map module 1054, and music player module1046, workout support module 1042 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store and transmit workoutdata.

In conjunction with touch screen 1012, display controller 1056, opticalsensor(s) 1064, optical sensor controller 1058, contact module 1030,graphics module 1032, and image management module 1044, camera module1043 includes executable instructions to capture still images or video(including a video stream) and store them into memory 1002, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 1002.

In conjunction with touch screen 1012, display controller 1056, contactmodule 1030, graphics module 1032, text input module 1034, and cameramodule 1043, image management module 1044 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, and textinput module 1034, browser module 1047 includes executable instructionsto browse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, e-mail client module 1040, and browser module 1047,calendar module 1048 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, and browser module 1047, widget modules 1049 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 1049-1, stocks widget 1049-2, calculator widget 1049-3,alarm clock widget 1049-4, and dictionary widget 1049-5) or created bythe user (e.g., user-created widget 1049-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, and browser module 1047, the widget creator module 1050 maybe used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 1012, display system controller 1056,contact module 1030, graphics module 1032, and text input module 1034,search module 1051 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 1002 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 1012, display system controller 1056,contact module 1030, graphics module 1032, audio circuitry 1010, speaker1011, RF circuitry 1008, and browser module 1047, video and music playermodule 1052 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 1012 or on an external, connected display via external port1024). In some embodiments, device 1000 may include the functionality ofan MP3 player, such as an IPOD (trademark of Apple Inc.).

In conjunction with touch screen 1012, display controller 1056, contactmodule 1030, graphics module 1032, and text input module 1034, notesmodule 1053 includes executable instructions to create and manage notes,to do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, GPS module 1035, and browser module 1047, map module 1054may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 1012, display system controller 1056,contact module 1030, graphics module 1032, audio circuitry 1010, speaker1011, RF circuitry 1008, text input module 1034, e-mail client module1040, and browser module 1047, online video module 1055 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 1024), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 1041, rather than e-mail client module 1040, isused to send a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 1002 maystore a subset of the modules and data structures identified above.Furthermore, memory 1002 may store additional modules and datastructures not described above.

In some embodiments, device 1000 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device1000, the number of physical input control devices (such as pushbuttons, dials, and the like) on device 1000 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 1000 to a main, home, or root menu from any userinterface that may be displayed on device 1000. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 6 is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 1002 (in FIG. 5) includes event sorter 1070 (e.g., in operatingsystem 1026) and a respective application 1036-1 (e.g., any of theaforementioned applications 1037-1051, 1055).

Event sorter 1070 receives event information and determines theapplication 1036-1 and application view 1091 of application 1036-1 towhich to deliver the event information. Event sorter 1070 includes eventmonitor 1071 and event dispatcher module 1074. In some embodiments,application 1036-1 includes application internal state 1092, whichindicates the current application view(s) displayed on touch sensitivedisplay 1012 when the application is active or executing. In someembodiments, device/global internal state 1057 is used by event sorter1070 to determine which application(s) is (are) currently active, andapplication internal state 1092 is used by event sorter 1070 todetermine application views 1091 to which to deliver event information.

In some embodiments, application internal state 1092 includes additionalinformation, such as one or more of: resume information to be used whenapplication 1036-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 1036-1, a state queue for enabling the user to go back toa prior state or view of application 1036-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 1071 receives event information from peripherals interface1018. Event information includes information about a sub-event (e.g., auser touch on touch sensitive display 1012, as part of a multi-touchgesture). Peripherals interface 1018 transmits information it receivesfrom I/O subsystem 1006 or a sensor, such as proximity sensor 1066,orientation sensor(s) 1068, and/or microphone 1013 (through audiocircuitry 1010). Information that peripherals interface 1018 receivesfrom I/O subsystem 1006 includes information from touch-sensitivedisplay 1012 or a touch-sensitive surface.

In some embodiments, event monitor 1071 sends requests to theperipherals interface 1018 at predetermined intervals. In response,peripherals interface 1018 transmits event information. In otherembodiments, peripheral interface 1018 transmits event information onlywhen there is a significant event (e.g., receiving an input above apredetermined noise threshold and/or for more than a predeterminedduration).

In some embodiments, event sorter 1070 also includes a hit viewdetermination module 1072 and/or an active event recognizerdetermination module 1073.

Hit view determination module 1072 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 1012 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 1072 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 1072identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 1073 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 1073 determines that only the hit view should receive aparticular sequence of sub-events. In other embodiments, active eventrecognizer determination module 1073 determines that all views thatinclude the physical location of a sub-event are actively involvedviews, and therefore determines that all actively involved views shouldreceive a particular sequence of sub-events. In other embodiments, evenif touch sub-events were entirely confined to the area associated withone particular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 1074 dispatches the event information to anevent recognizer (e.g., event recognizer 1080). In embodiments includingactive event recognizer determination module 1073, event dispatchermodule 1074 delivers the event information to an event recognizerdetermined by active event recognizer determination module 1073. In someembodiments, event dispatcher module 1074 stores in an event queue theevent information, which is retrieved by a respective event receivermodule 1082.

In some embodiments, operating system 1026 includes event sorter 1070.Alternatively, application 1036-1 includes event sorter 1070. In yetother embodiments, event sorter 1070 is a stand-alone module, or a partof another module stored in memory 1002, such as contact/motion module1030.

In some embodiments, application 1036-1 includes multiple event handlers1090 and one or more application views 1091, each of which includesinstructions for handling touch events that occur within a respectiveview of the application's user interface. Each application view 1091 ofthe application 1036-1 includes one or more event recognizers 1080.Typically, a respective application view 1091 includes multiple eventrecognizers 1080. In other embodiments, one or more of event recognizers1080 are part of a separate module, such as a user interface kit (notshown) or a higher level object from which application 1036-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 1090 includes one or more of: data updater 1076, object updater1077, GUI updater 1078, and/or event data 1079 received from eventsorter 1070. Event handler 1090 may utilize or call data updater 1076,object updater 1077 or GUI updater 1078 to update the applicationinternal state 1092. Alternatively, one or more of the application views1091 includes one or more respective event handlers 1090. Also, in someembodiments, one or more of data updater 1076, object updater 1077, andGUI updater 1078 are included in a respective application view 1091.

A respective event recognizer 1080 receives event information (e.g.,event data 1079) from event sorter 1070, and identifies an event fromthe event information. Event recognizer 1080 includes event receiver1082 and event comparator 1084. In some embodiments, event recognizer1080 also includes at least a subset of: metadata 1083, and eventdelivery instructions 1088 (which may include sub-event deliveryinstructions).

Event receiver 1082 receives event information from event sorter 1070.The event information includes information about a sub-event, forexample, a touch or a touch movement. Depending on the sub-event, theevent information also includes additional information, such as locationof the sub-event. When the sub-event concerns motion of a touch theevent information may also include speed and direction of the sub-event.In some embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 1084 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 1084 includes eventdefinitions 1086. Event definitions 1086 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(1087-1), event 2 (1087-2), and others. In some embodiments, sub-eventsin an event 1087 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (1087-1) is a double tap on a displayed object.The double tap, for example, includes a first touch (touch begin) on thedisplayed object for a predetermined phase, a first lift-off (touch end)for a predetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(1087-2) is a dragging on a displayed object. The dragging, for example,includes a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 1012, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 1090.

In some embodiments, event definition 1087 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 1084 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 1012, when a touch is detected ontouch-sensitive display 1012, event comparator 1084 performs a hit testto determine which of the three user-interface objects is associatedwith the touch (sub-event). If each displayed object is associated witha respective event handler 1090, the event comparator uses the result ofthe hit test to determine which event handler 1090 should be activated.For example, event comparator 1084 selects an event handler associatedwith the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 1087 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 1080 determines that the series ofsub-events do not match any of the events in event definitions 1086, therespective event recognizer 1080 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 1080 includesmetadata 1083 with configurable properties, flags, and/or lists thatindicate how the event delivery system should perform sub-event deliveryto actively involved event recognizers. In some embodiments, metadata1083 includes configurable properties, flags, and/or lists that indicatehow event recognizers may interact with one another. In someembodiments, metadata 1083 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 1080 activates eventhandler 1090 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 1080 delivers event information associated with theevent to event handler 1090. Activating an event handler 1090 isdistinct from sending (and deferred sending) sub-events to a respectivehit view. In some embodiments, event recognizer 1080 throws a flagassociated with the recognized event, and event handler 1090 associatedwith the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 1088 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 1076 creates and updates data used inapplication 1036-1. For example, data updater 1076 updates the telephonenumber used in contacts module 1037, or stores a video file used invideo player module 1045. In some embodiments, object updater 1077creates and updates objects used in application 1036-1. For example,object updater 1076 creates a new user-interface object or updates theposition of a user-interface object. GUI updater 1078 updates the GUI.For example, GUI updater 1078 prepares display information and sends itto graphics module 1032 for display on a touch-sensitive display.

In some embodiments, event handler(s) 1090 includes or has access todata updater 1076, object updater 1077, and GUI updater 1078. In someembodiments, data updater 1076, object updater 1077, and GUI updater1078 are included in a single module of a respective application 1036-1or application view 1091. In other embodiments, they are included in twoor more software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 1000 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 7 illustrates a portable multifunction device 1000 having a touchscreen 1012 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 1200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making a gesture on the graphics, for example,with one or more fingers 1202 (not drawn to scale in the figure) or oneor more styluses 1203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thegesture may include one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 1000. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

Device 1000 may also include one or more physical buttons, such as“home” or menu button 1204. As described previously, menu button 1204may be used to navigate to any application 1036 in a set of applicationsthat may be executed on device 1000. Alternatively, in some embodiments,the menu button is implemented as a soft key in a GUI displayed on touchscreen 1012.

In one embodiment, device 1000 includes touch screen 1012, menu button1204, push button 1206 for powering the device on/off and locking thedevice, volume adjustment button(s) 1208, Subscriber Identity Module(SIM) card slot 1210, head set jack 1212, and docking/charging externalport 1024. Push button 1206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 1000 also may accept verbal inputfor activation or deactivation of some functions through microphone1013.

It should be noted that, although many of the following examples will begiven with reference to inputs on touch screen 1012 (where the touchsensitive surface and the display are combined), a touch-sensitivesurface that is separate from the display may be used instead of touchscreen 1012.

Example Mapping Functionality

FIG. 8 illustrates another example of a multifunction device, which maybe configured in a manner similar to the multifunction device describedabove. In the illustrated embodiment, a multifunction device 1400includes a mapping application (e.g., map module 1054 described above)that may be stored in one or more memories of multifunction device 1400and executed on one or more processors of multifunction device 1400. Asis the case for the multifunction device described above, multifunctiondevice 1400 may include one or more controls 1402 for operating themultifunction device. These controls may include but are not limited topower controls for turning the device on and off, volume controls foradjusting the ear piece volume or the speaker volume, menu controls fornavigation functions of the device, and function controls for initiatingone or more function or actions on the device. Controls 1402 may includehardware controls or software controls. For instance, the bottom leftcorner of electronic display 1412 includes a graphical representation ofa control 1412 that may be selected by a user, such as by way of touchin accordance with the touch screen functionality described above.Multifunction device 1400 may also include other components similar tothose described above, such as a microphone 1404, an earpiece 1406(e.g., a speaker through which to convey audio representations oftelephone calls), an optical sensor 1408, and/or a speaker 1410. Each ofthese components may be configured in a similar manner to thoselike-named components of FIG. 7 described above. Furthermore, electronicdisplay 1412 may be configured with touch screen capability, such astouch screen 1012 described above. In various embodiments, controls(e.g., on screen control(s) 1402) may be utilized to perform any of avariety of map-related functions including but not limited to zoom in,zoom out, rotate screen, pan screen, toggle views (e.g., two-dimensionsto three dimensions and vice versa), and/or another map relatedactivity. In various embodiments, one or more gestures may be utilizedto perform any of the aforesaid map controls (with or without the use ofan actual graphical on-screen control). In one non-limiting example, aone figure gesture may be utilized to adjust the pitch within athree-dimensional map view.

As noted above, multifunction device 1400 includes a mapping applicationthat may be stored in one or more memories of multifunction device 1400and executed on one or more processors of multifunction device 1400. Inthe illustrated embodiment, the graphical representation of the mappingapplication may include a map 1414 of a geographic region. This map maybe presented as a two-dimensional map or a three-dimensional map, theselection of which may be specified through, e.g., a user-configurableparameter of the mapping application. In some embodiments, themultifunction device may toggle between two-dimensional map orthree-dimensional map views responsive to input from any input componentof the multifunction device. In one non-limiting example, input fromorientation sensor(s) 1068 may initiate the transition from atwo-dimensional map view to a three-dimensional map, and vice versa. Forinstance, one or more of orientation sensor(s) 1068 may detect a tilt(e.g., a user-initiated tilt) in the orientation of the multifunctiondevice and, in response, initiate the aforesaid toggling.

Map 1414 may include a graphical position indicator 1416, which mayrepresent the location of the multifunction device within the geographicregion of the map. Generally position indicator 1416 may represent thecurrent or real-time position of the multifunction device, although itshould be understood that in some cases there may exist some smallamount of temporal latency between the actual position of themultifunction device and the graphical representation of that location(e.g., position indicator 1416). This may occur, e.g., when themultifunction device is in motion. In various embodiments, themultifunction device may be configured to perform map matching includingbut not limited to aligning a sequence of observed user positions with aroad network on a digital map. In various embodiments, the multifunctiondevice may be configured to perform a “snap to” function in which thegraphical position indicator 1416 is aligned onto a roadway when theuser's position falls within in a specified threshold distance of theroadway.

Furthermore, multifunction device 1400 may generally be operated by auser. For example, multifunction device 1400 may in some cases be asmartphone utilized by an individual to make phone calls, send textmessages, browse the internet, etc. As use of multifunction device by anindividual generally implies the individual is proximate to themultifunction device (e.g., the user may be holding the device in his orher hand), references herein to the location of the device and thelocation of the user may be considered to be synonymous. However, itshould be understood that in some cases the actual position of themultifunction device and the user of that device may differ by somedistance. For instance, the user may place his or her multifunctiondevice on a table of an outdoor café while sitting in a nearby chair. Inthis case, the position of the device and the position of the user maydiffer by some small amount. In another example, multifunction device1400 may be mounted on a car dashboard (e.g., for use as a navigationdevice) while the user of the device sits nearby (e.g., in the driverseat of the car). In this case as well, the position of the device andthe position of the user may differ by some small amount. Despite thesesmall differences in position, generally the position of themultifunction device and the position of the multifunction device usermay be considered to coincide.

In various embodiments, the map 1414 displayed by the multifunctiondevice may include one or more roads (e.g., roads 1418 a-b), buildings(not illustrated), terrain features (e.g., hills, mountains) (notillustrated), parks (not illustrated), water bodies (not illustrated),and/or any other item that may be conveyed by a map. In some cases, themap may also include other map or navigation information including butlimited to readouts from one or more of a directional compass, analtimeter, and/or a thermometer.

In various embodiments, the mapping application may be configured togenerate directions from an origination (e.g., an address or a user'scurrent position) to a destination (e.g., an address, landmark,bookmarked/saved location, or point of interest). For instance, anindication of the origination and/or destination may be input into themulti-function device by the user. The multifunction device may generateone or more candidate routes between those two points. The multifunctiondevice may select one of those routes for display on the device. Inother cases, multiple candidate routes may be presented to the user andthe user may select a preferred route. In the illustrated embodiment,one route is illustrated as route 1420. The route may also includeturn-by-turn directions which may be presented to the user (in 2D or3D), such as a graphical indication to perform a turn 1422 a from road1418 a to road 1418 b. In some embodiments, this graphical indication toperform a turn may be supplemented or substituted with an audibleindication to turn, such as a voice command from speaker 1410 thatindicates the user is to “turn left in 100 yards,” for example. In someembodiments, the route that is selected may be presented to the user asa route overview. For instance, before proceeding with navigation, themultifunction device may generate a route overview display thatgraphically indicates key information for the route, such as key turns,route distance and/or an estimated time for traversing the route. Insome cases, the multifunction device may be configured to generate adisplay of driving maneuvers (e.g., turns, lane changes, etc.) thatoccur in quick succession, either in the route overview or during actualnavigation. This information may help the user safely prepare for suchmaneuvers. In some cases, the route information may be presented in alist format, such as a list of turns or other maneuvers.

In various embodiments, the mapping application of the multifunctiondevice may be configured to track the position of the user over time andcorrespondingly adjust the graphical position indicator 1416 to indicatethe new position. For instance, the mapping application may determinethat the user is traveling along route 1420 from position information(e.g., information from GPS module 1035) and update the map 1414accordingly. For instance, in some cases the map 1414 may remainstationary while position indicator 1416 is moved along the route. Inother cases, position indicator 1416 may remain stationary or “fixed”while map 1414 is moved (e.g., panned, turned, etc.) around the positionindicator.

In various embodiments, the multifunction device may be configured todisplay alternate or contingency routes. In some cases, these routes maybe selectable by the user (e.g., via the touch screen interface). Inother cases, the multifunction device may select a best route based onone or more parameters, such as shortest distance or time. In somecases, these parameters or preferences may be set by the user.

As described in more detail below, the multifunction device may invarious embodiments receive routing information that specifies a routefrom a map service. In some case, the multifunction device may carry outnavigation guidance in accordance with this route. However, in somecases, the multifunction device may perform a reroute operation in orderto generate a new route to the destination. For instance, the user mayhave deviated from the original route or explicitly requested a newroute. In some cases, the multifunction device may perform reroutingbased on cached map data stored on the multifunction device.

In various embodiments, the multifunction device may be configured toperform route correction based on real-time data, such as updates in mapinformation, road conditions, traffic conditions, and/or weatherconditions. For instance, the multifunction device may be configured toalter a route such that the route avoids a construction zone or adangerous storm cell.

In various embodiments, the multifunction device may be configured toperform lane guidance independently or as part of navigation guidance.For instance, the multifunction device may, in response to detectingthat multiple turns follow in quick succession, provide the user with adirection or suggestion as to which lane to occupy. For instance, avoice or visual indication may specify that the user “turn right, thenmove to the left lane” in anticipation of a subsequent left turn. Inanother example, the multifunction device may detect one or more laneclosures (e.g., due to construction or other reasons) and instruct theuser to avoid such lanes.

In various embodiments, the multifunction device may be configured togenerate voice prompts for directions. For instance, during navigationguidance, the multifunction device may be configured to generate audiorepresentations of the next turn or driving maneuver on the route. Forinstance, the multifunction device may be configured to audibly indicatethe user should “turn left in 100 yards” or some other audibleindication of a maneuver.

In various embodiments, the multifunction device may be responsive tovarious voice commands for performing actions including a command toobtain a route. For instance, the multifunction device may interpret theuser's voice through a microphone or other transducer of themultifunction device. The user may specify an origination and adestination for the requested route. In various embodiments, themultifunction device may be configured to utilize the user's currentlocation as the origination for the route.

In various embodiments, the multifunction device may be configured toperform a search along a specific route, such as current navigationroute. For instance, the user of the multifunction device may requestthe location of points of interest, such as fuel stations orrestaurants. However, if a user is traveling along a particular route,they may not be particularly interested in points of interest that arenot proximate to that route. As such, the multifunction device may beconfigured to scope any searches to points of interested within aspecified distance away from the route. In various embodiments, thisdistance may be a configurable parameter.

In various embodiments, the multifunction device may be configured todisplay various graphical layers including but not limited to agraphical map information, aerial images (e.g., satellite-acquiredimages), and/or traffic information. For instance, in the trafficinformation example, the multifunction device may overlay color codedtraffic information on roadways to indicate the speed at which trafficis flowing. For example, green color coding may be used to indicatetraffic is flowing normally, and yellow or red may be used to indicatetraffic slowdowns.

In various embodiments, the multifunction device may be configured todisplay any quantity of metrics or statistics about a navigation routeincluding but not limited to an estimated time of arrival, traveldistance remaining, average speed (overall or moving average), topspeed, and/or other route statistics.

In various embodiments, the multifunction device may be configured todisplay routes at different angles in order to accommodate thepreferences of different users. Such viewing angles may include a bird'seye view for two-dimensional maps to any of a variety of camera anglesavailable for a three-dimensional map.

In various embodiments, the multifunction device may be configured toprovide navigation information other than map and routing information.For instance the multifunction device may expose output from any of thehardware device described above with respect to FIG. 5. In onenon-limiting example, an orientation sensor 1068 may include a compassthat outputs direction data. The multifunction device described hereinmay be configured to display this directional data as a virtual compass,for example.

Example System

Embodiments of the method for dynamically generating map textures asdescribed herein may be executed on one or more computer systems such asthe map service 130 or a client device 102 in FIG. 1, which may interactwith various other devices. One such computer system is illustrated byFIG. 9. In different embodiments, computer system 2000 may be any ofvarious types of devices, including, but not limited to, a personalcomputer system, desktop computer, laptop, notebook, or netbookcomputer, mainframe computer system, handheld computer, workstation,network computer, a camera, a set top box, a mobile device, a consumerdevice, video game console, handheld video game device, applicationserver, storage device, a peripheral device such as a switch, modem,router, or in general any type of computing or electronic device.

In the illustrated embodiment, computer system 2000 includes one or moreprocessors 2010 coupled to a system memory 2020 via an input/output(I/O) interface 2030. Computer system 2000 further includes a networkinterface 2040 coupled to I/O interface 2030, and one or moreinput/output devices 2050, such as cursor control device 2060, keyboard2070, display(s) 2080, and touch-sensitive device 2090. In someembodiments, it is contemplated that embodiments may be implementedusing a single instance of computer system 2000, while in otherembodiments multiple such systems, or multiple nodes making up computersystem 2000, may be configured to host different portions or instancesof embodiments. For example, in one embodiment some elements may beimplemented via one or more nodes of computer system 2000 that aredistinct from those nodes implementing other elements.

In various embodiments, computer system 2000 may be a uniprocessorsystem including one processor 2010, or a multiprocessor systemincluding several processors 2010 (e.g., two, four, eight, or anothersuitable number). Processors 2010 may be any suitable processor capableof executing instructions. For example, in various embodiments,processors 2010 may be general-purpose or embedded processorsimplementing any of a variety of instruction set architectures (ISAs),such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitableISA. In multiprocessor systems, each of processors 2010 may commonly,but not necessarily, implement the same ISA.

In some embodiments, at least one processor 2010 may be a graphicsprocessing unit. A graphics processing unit or GPU may be considered adedicated graphics-client device for a personal computer, workstation,game console or other computing or electronic device. Modern GPUs may bevery efficient at manipulating and displaying computer graphics, andtheir highly parallel structure may make them more effective thantypical CPUs for a range of complex graphical algorithms. For example, agraphics processor may implement a number of graphics primitiveoperations in a way that makes executing them much faster than drawingdirectly to the screen with a host central processing unit (CPU). Invarious embodiments, the image processing methods disclosed herein may,at least in part, be implemented by program instructions configured forexecution on one of, or parallel execution on two or more of, such GPUs.The GPU(s) may implement one or more application programmer interfaces(APIs) that permit programmers to invoke the functionality of theGPU(s). Suitable GPUs may be commercially available from vendors such asNVIDIA Corporation, ATI Technologies (AMD), and others.

System memory 2020 may be configured to store program instructionsand/or data accessible by processor 2010. In various embodiments, systemmemory 2020 may be implemented using any suitable memory technology,such as static random access memory (SRAM), synchronous dynamic RAM(SDRAM), nonvolatile/Flash-type memory, or any other type of memory. Inthe illustrated embodiment, program instructions and data implementingdesired functions, such as those described above for embodiments of themethod for rendering a map according to a stylesheet as described hereinare shown stored within system memory 2020 as program instructions 2025and data storage 2035, respectively. In other embodiments, programinstructions and/or data may be received, sent or stored upon differenttypes of computer-accessible media or on similar media separate fromsystem memory 2020 or computer system 2000. Generally speaking, acomputer-accessible medium may include storage media or memory mediasuch as magnetic or optical media, e.g., disk or CD/DVD-ROM coupled tocomputer system 2000 via I/O interface 2030. Program instructions anddata stored via a computer-accessible medium may be transmitted bytransmission media or signals such as electrical, electromagnetic, ordigital signals, which may be conveyed via a communication medium suchas a network and/or a wireless link, such as may be implemented vianetwork interface 2040.

In one embodiment, I/O interface 2030 may be configured to coordinateI/O traffic between processor 2010, system memory 2020, and anyperipheral devices in the device, including network interface 2040 orother peripheral interfaces, such as input/output devices 2050. In someembodiments, I/O interface 2030 may perform any necessary protocol,timing or other data transformations to convert data signals from onecomponent (e.g., system memory 2020) into a format suitable for use byanother component (e.g., processor 2010). In some embodiments, I/Ointerface 2030 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of I/Ointerface 2030 may be split into two or more separate components, suchas a north bridge and a south bridge, for example. In addition, in someembodiments some or all of the functionality of I/O interface 2030, suchas an interface to system memory 2020, may be incorporated directly intoprocessor 2010.

Network interface 2040 may be configured to allow data to be exchangedbetween computer system 2000 and other devices attached to a network,such as other computer systems, or between nodes of computer system2000. In various embodiments, network interface 2040 may supportcommunication via wired or wireless general data networks, such as anysuitable type of Ethernet network, for example; viatelecommunications/telephony networks such as analog voice networks ordigital fiber communications networks; via storage area networks such asFibre Channel SANs, or via any other suitable type of network and/orprotocol.

Input/output devices 2050 may, in some embodiments, include one or moredisplay terminals, keyboards, keypads, touchpads, scanning devices,voice or optical recognition devices, or any other devices suitable forentering or retrieving data by one or more computer system 2000.Multiple input/output devices 2050 may be present in computer system2000 or may be distributed on various nodes of computer system 2000. Insome embodiments, similar input/output devices may be separate fromcomputer system 2000 and may interact with one or more nodes of computersystem 2000 through a wired or wireless connection, such as over networkinterface 2040.

As shown in FIG. 9, memory 2020 may include program instructions 2025,configured to implement embodiments of the method for rendering a mapaccording to texture masks as described herein, and data storage 2035,comprising various data accessible by program instructions 2025. In oneembodiment, program instructions 2025 may include software elements ofembodiments of the method for dynamically generating map textures. Datastorage 2035 may include data that may be used in embodiments. In otherembodiments, other or different software elements and data may beincluded.

Those skilled in the art will appreciate that computer system 2000 ismerely illustrative and is not intended to limit the scope of the methodfor rendering a map according to a stylesheet as described herein. Inparticular, the computer system and devices may include any combinationof hardware or software that can perform the indicated functions,including a computer, personal computer system, desktop computer,laptop, notebook, or netbook computer, mainframe computer system,handheld computer, workstation, network computer, a camera, a set topbox, a mobile device, network device, internet appliance, PDA, wirelessphones, pagers, a consumer device, video game console, handheld videogame device, application server, storage device, a peripheral devicesuch as a switch, modem, router, or in general any type of computing orelectronic device. Computer system 2000 may also be connected to otherdevices that are not illustrated, or instead may operate as astand-alone system. In addition, the functionality provided by theillustrated components may in some embodiments be combined in fewercomponents or distributed in additional components. Similarly, in someembodiments, the functionality of some of the illustrated components maynot be provided and/or other additional functionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 2000 may be transmitted to computer system2000 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network and/or a wireless link. Various embodiments mayfurther include receiving, sending or storing instructions and/or dataimplemented in accordance with the foregoing description upon acomputer-accessible medium. Accordingly, the present invention may bepracticed with other computer system configurations.

What is claimed is:
 1. A method, comprising: performing, by a computingdevice remote from a server: obtaining from the server, by a geographicmapping application implemented on the computing device, a map tile of ageographic map, wherein the map tile comprises vector graphics datadescribing one or more shapes for a geographic map and one or moretexture identifiers for the one or shapes, but does not includerespective textures for the one or more shapes; and rendering a mapview, based on the obtained map tile, for displaying at least a portionof the geographic map on the computing device, wherein said renderingthe map view comprises automatically performing by the computing device:for one or more of the one or more shapes described for the geographicmap: obtaining, from the server or another server, via a wirelessnetwork, based on a texture identifier corresponding to the shape, atexture definition for dynamically generating, at the computing device,a particular texture for the shape or obtaining, from a storage of thecomputing device, based on the texture identifier corresponding to theshape, a texture definition previously obtained via the wireless networkfor dynamically generating, at the computing device, the particulartexture for the shape; dynamically generating, by the computing device,the particular texture for the shape according to the texture definitionor the previously obtained texture definition instead of downloading theparticular texture via the wireless network, wherein dynamicallygenerating the particular texture comprises combining a plurality ofvarying elements according to the texture definition; and applying thegenerated particular texture to the shape to render a current fillportion of the shape in the map view.
 2. The method of claim 1, whereinsaid dynamically generating the particular texture for the shapeaccording to the texture definition or the previously obtained texturedefinition comprises: obtaining a base texture layer according to thetexture definition or the previously obtained texture definition;obtaining one or more noise texture elements or pattern texture elementsaccording to the texture definition or the previously obtained texturedefinition; and combining the base texture layer with the one or morenoise texture elements or pattern texture elements to generate theparticular texture for the shape, wherein the plurality of varyingelements in the generated particular texture comprise the one or morenoise texture elements or pattern texture elements.
 3. The method ofclaim 2, wherein the base texture layer is a color value.
 4. The methodof claim 2, wherein at least one of the one or more noise textureelements are generated according to the texture definition or thepreviously obtained texture definition.
 5. The method of claim 1,further comprising storing in local texture data storage the particulargenerated texture or one or more additional generated textures.
 6. Themethod of claim 1, further comprising: in response to receiving anindication of a particular zoom level for the map view: varying thecurrent fill portion for the shape, wherein said varying comprises:obtaining a second texture definition, based on the texture identifiercorresponding to the shape, for dynamically generating another texturefor the shape according to the indicated zoom level; dynamicallygenerating the other texture for the shape according to the secondtexture definition; and applying the generated other texture to theshape to render the current fill portion of the shape.
 7. Anon-transitory, computer-readable storage medium, storing programinstructions, wherein the program instructions are computer-executableto implement a geographic map application configured to: obtain from aserver, by the geographic map application, a map tile of a geographicmap, wherein the map tile comprises vector graphics data describing oneor more shapes for a geographic map and one or more texture identifiersfor the one or shapes, but does not include respective textures for theone or more shapes; and render a map view based on the obtained map tilefor display on a computing device, wherein said rendering the map viewcomprises automatically performing: for one or more of the one or moreshapes described for the map: obtaining from the server or anotherserver, via a wireless network, based on a texture identifiercorresponding to the shape, a texture definition for dynamicallygenerating, at the computing device, a particular texture for the shapeor obtain, from a storage of the computing device, based on the textureidentifier corresponding to the shape, a texture definition previouslyobtained via the wireless network for dynamically generating, at thecomputing device, the particular texture for the shape; dynamicallygenerating, by the computing device, the particular texture for theshape according to the texture definition or the previously obtainedtexture definition instead of downloading the particular texture via thewireless network, wherein dynamically generating the particular texturecomprises combining a plurality of varying elements according to thetexture definition; and applying the generated particular texture to theshape to render a current fill portion of the shape in the map view. 8.The medium of claim 7, wherein to dynamically generate the particulartexture for the shape according to the texture definition or thepreviously obtained texture definition, the program instructions arefurther computer-executable to implement a geographic map applicationconfigured to: obtain a base texture layer according to the texturedefinition or the previously obtained texture definition; obtain one ormore noise texture elements or pattern texture elements according to thetexture definition or the previously obtained texture definition; andcombine the base texture layer with the one or more noise textureelements or pattern texture elements to generate the particulargenerated texture for the shape, wherein the plurality of varyingelements in the generated particular texture comprise the one or morenoise texture elements or pattern texture elements.
 9. The medium ofclaim 8, wherein at least two of the shapes described for the geographicmap are linked to the same texture identifier, and wherein todynamically generate the particular texture for the shape according tothe texture definition or the previously obtained texture definition,the program instructions are further computer-executable to implement ageographic map application configured to vary at least one of the basetexture layers or at least one of the one or more noise texture elementsor pattern textures elements as specified in the texture definition orthe previously obtained texture definition for one or more of the atleast two shapes in order to generate different textures for the atleast two shapes.
 10. The medium of claim 7, wherein the programinstructions are further computer-executable to implement a geographicmap application configured to: in response to receiving an indication ofa change in the texture definition or the previously obtained texturedefinition: vary the current fill portion for one of the shapes, whereinsaid vary comprises: dynamically generate another texture for the shapeaccording to the changed texture definition; and apply the generatedother texture to the shape to render the current fill portion of theshape.
 11. The medium of claim 7, wherein at least one particulartexture definition for dynamically generating a particular texturecomprises a sequence of texture specifications, and wherein todynamically generate a particular texture for the shape according to thetexture definition or the previously obtained texture definition, theprogram instructions are further computer-executable to generate asequence of particular textures for the shape in order to render atexture animation for the shape.
 12. A multi-function device,comprising: a touch-sensitive display; one or more processors; and oneor more memories storing a geographic map application executable on theone or more processors to: obtain a map tile of a geographic map from aserver remote from the multi-function device, wherein the map tilecomprises vector graphics data describing one or more shapes for ageographic map and texture identifiers linked to the one or more shapes,but does not include respective textures for the one or more shapes; andrender a map view based on the obtained map tile for display on thetouch-sensitive display, comprising automatically performing: for one ormore of the one or more shapes described for the map: obtain, from theserver or another server, via a wireless network, a particular texturedefinition for the shape based on a texture identifier linked to theshape, wherein the particular texture definition specifies one or moreelements to be used to dynamically generate, at the multi-functiondevice, a texture for the shape, or obtain, from a storage of themulti-function device, the particular texture definition for the shape,wherein the particular texture definition was previously obtained fromthe server or the other server via the wireless network; dynamicallygenerate, at the multi-function device, the texture for the shapeaccording to the particular texture definition instead of downloadingthe particular texture via the wireless network, wherein dynamicallygenerating the texture comprises combining a plurality of varyingelements; and apply the generated texture to the shape to render acurrent fill portion of the shape in the map view.
 13. The device ofclaim 12, wherein, to dynamically generate the texture for the shapeaccording to the particular texture definition, the geographic mapapplication is further executable on the one or more processors to blenda base texture layer specified in the texture definition with one ormore noise texture elements or pattern texture elements specified in thetexture definition to generate the texture, wherein the plurality ofvarying elements in the generated texture comprise the one or more noisetexture elements or pattern texture elements.
 14. The device of claim12, wherein the geographic map application is further executable on theone or more processors to: in response to receiving an indication of aparticular map view mode: vary the current fill portion for one of theshapes, wherein said varying comprises: obtain a second texturedefinition for the shape according to the indicated map view mode;dynamically generate another texture for the shape according to thesecond texture definition; and apply the generated other texture to theshape to render the current fill portion of the shape.
 15. The device ofclaim 12, wherein the geographic map application is further executableon the one or more processors to display the rendered map view on thetouch-sensitive display.
 16. The device of claim 12, wherein the one ormore memories further store program instructions executable on the oneor more processors to implement: a geo-location component configured todetermine the current location of the multi-function device; wherein, toobtain a particular texture definition for the shape based on a textureidentifier linked to the shape, the geographic map application isfurther executable on the one or more processors to determine thetexture identifier linked to the shape based on the current locationprovided by the geo-location component.
 17. The device of claim 12,wherein the geographic map application is further executable on the oneor more processors to: in response to receiving an indication of achange in a previously obtained texture definition: vary the currentfill portion for one of the shapes, wherein said varying comprises:dynamically generate another texture for the shape according to thechanged texture definition; and apply the generated other texture to theshape to render the current fill portion of the shape.
 18. The device ofclaim 17, wherein the one or more memories further store programinstructions executable on the one or more processors to implement: atime component configured to determine a current time of themulti-function device; wherein the change in the particular texturedefinition occurs in response to the current time of the multi-functiondevice.